At Intersoft Solutions, we constantly conduct extensive research and development to deliver new innovations that help developers become more productive by reducing the efforts and overwhelming complexity in both development and deployment stage.
The brand-new SmartWebResources�?� Framework is one of the exciting technology that we had to offer in 2007 R1 platform. The key objective of SmartWebResources�?� is to eliminate the external physical resources �?? such as scripts, images, etc �?? which required by web components to function properly.
Problems introduced in traditional web components approach
Most web components require client resources such as scripts, images, stylesheets and other client files to gear up some advanced and powerful features. Normally these client resources are delivered through physical client files. In ASP.NET, these files may be located in aspnet_client folder or other common folder which needs to be mapped properly into IIS virtual path in order to function properly.
There are several issues with this traditional approach which causing inefficiency, such as:
- Special IIS virtual directory is required to store the client resources. In several webhosting that does not support manual virtual directory setup, this can be a significant deployment problem.
- Special attention and more efforts are required during deployment.
- Versioning problems. This could cause overwhelming complexity while maintaining the versions of the client resources for specific components.
- Complexity in maintaining control-specific�??s resources folder. For instance, some scripts are located in folder X, images in folder Y, and other scripts in folder Z.
The solution
The solution to the several issues mentioned above can be achieved by eliminating the requirements to use physical client resources. Thanks to the new SmartWebResources�?� Framework, the physical client resources can be completely eliminated.
 |
The client resources are still required in our web components. It is just they are now stored in �??virtual location�?� which does not require the awareness of developers. They are fetched and delivered to client (browsers) in a new, different way. |